-
Notifications
You must be signed in to change notification settings - Fork 91
Improve readability when printing type of classes in error messages #469
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
Signed-off-by: ijnek <[email protected]>
|
Pulls: #469 |
|
https://github.com/Mergifyio backport kilted jazzy humble |
✅ Backports have been created
|
Signed-off-by: ijnek <[email protected]> (cherry picked from commit 9c5f6a7)
Signed-off-by: ijnek <[email protected]> (cherry picked from commit 9c5f6a7)
Signed-off-by: ijnek <[email protected]> (cherry picked from commit 9c5f6a7) # Conflicts: # launch_ros/launch_ros/utilities/evaluate_parameters.py
(cherry picked from commit 9c5f6a7) Signed-off-by: ijnek <[email protected]> Co-authored-by: Kenji Brameld <[email protected]>
(cherry picked from commit 9c5f6a7) Signed-off-by: ijnek <[email protected]> Co-authored-by: Kenji Brameld <[email protected]>
Description
Similar to ros2/launch#887, in a few places, error messages printed types in a verbose format like '<class 'str'>'. This PR simplifies that by displaying just the type name (e.g. 'str').
Did you use Generative AI?
No